Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1526

reference
242-tree-1
name
1526
tree-preservation-order

undefined

242-tpo-1
uprn
address-text
point
POINT (-1.005283 50.854335)
geometry
MULTIPOLYGON (((-1.005226 50.854329,-1.005228 50.854340,-1.005236 50.854350,-1.005249 50.854358,-1.005264 50.854363,-1.005282 50.854365,-1.005300 50.854363,-1.005316 50.854358,-1.005328 50.854351,-1.005337 50.854341,-1.005340 50.854330,-1.005337 50.854318,-1.005329 50.854308,-1.005317 50.854300,-1.005301 50.854295,-1.005283 50.854293,-1.005266 50.854295,-1.005250 50.854300,-1.005237 50.854308,-1.005229 50.854318,-1.005226 50.854329)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL